@shawnborton @allroundexperts One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

Pinging @Santhosh-Sellavel here because he reviewed all the other SelectionList refactor PRs

@thiagobrez @Santhosh-Sellavel is OoO. I can help the review here!

Awesome, thank you @allroundexperts!

For context: Shawn said here to change to this behavior

Sounds good!

Reviewer Checklist

• I have verified the author checklist is complete (all boxes are checked off).
• I verified the correct issue is linked in the ### Fixed Issues section above
• I verified testing steps are clear and they cover the changes made in this PR
  • I verified the steps for local testing are in the Tests section
  • I verified the steps for Staging and/or Production testing are in the QA steps section
  • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
• I checked that screenshots or videos are included for tests on all platforms
• I included screenshots or videos for tests on all platforms
• I verified tests pass on all platforms & I tested again on:
  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop
• If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
• I verified proper code patterns were followed (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
  • I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I verified that this PR follows the guidelines as stated in the Review Guidelines
• I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
• I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Looks good to me, thanks!

@thiagobrez The item remains highlighted even if you un-select it. Can you please check?

Hey @allroundexperts, what is the expected behavior though?

I'm not sure. But this does not look right. If you've unselected the row, the highlight should not stick. If you can confirm that this is expected, then I can continue with the review.

I got you, this is new behavior and I don't have enough information to answer that. We'll need @shawnborton to check this

Yeah, the only highlight we want to remain is the highlight used when moving around with the arrow keys. The highlight indicates what row is active in terms of arrow navigation. And we decided that it is weird that if you check or uncheck a row that your active row would change. Basically you should not lose position of your active row as you toggle things on or off if you are using the arrow keys.

So I think @allroundexperts is right above.

@shawnborton

Basically you should not lose position of your active row as you toggle things on or off if you are using the arrow keys.

Ok, so if I understand correct, while you're navigating with the keyboard, either activating or deactivating you should never loose the active row.

The problem currently is when clicking/pressing. If I click to activate, the row should get highlighted. If I click to deactivate, the highlight should disappear.

Is that how it should behave ⬆️ ?

I think that makes sense. Although, how does click to highlight work today?

@shawnborton @allroundexperts I understand the source of confunsion now. When clicking the item, it was showing an "active" highlight, same as if you were hovering it, which is not the same as the highlight for when you're moving with the arrow keys. I removed that, which fixes what @allroundexperts mentioned above, and makes it much cleaner.

Also included in the commit a fix for the Enter hotkey event, which was not working as expected when we had accessibility selection active.

Here's a video in action:

That looks perfect, thanks!

@allroundexperts Friendly reminder here

On it now!

This is still not working as intended. At the end of this video, notice that selecting a new row does not unselect the old one.

@allroundexperts Ok - sent fixes, please review again!

Heads up: I'll be OOO from tomorrow until Tuesday - if needed, someone from Callstack can continue here!

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/cristipaval in version: 1.3.75-0 🚀

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.75-12 🚀

🚀 Deployed to staging by https://github.com/cristipaval in version: 1.3.76-0 🚀

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.76-6 🚀